Method and system for verifying a recording

ABSTRACT

A system for verifying a recording. The system comprises at least one processor, at least one non-transitory computer readable storage medium storing instructions thereon that, when executed by the at least one processor, cause the system to verify an electronic recording file comprising a cryptographic hash function based on the recording and generated by a first electronic device, verifying the electronic recording file comprises generating a pair of certification requests. A first of the pair of certification requests is based on the cryptographic hash function, and a second of the pair of certification requests is based on the cryptographic hash function in combination with one or more further pieces of data associated with the recording. The one or more further pieces of data comprise metadata associated with the recording and/or the first electronic device, sending the pair of certification requests to a blockchain, and receiving confirmation of the approval of the pair of certification requests by the blockchain.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of co-pending U.S. application Ser.No. 16/126,198 filed on Sep. 10, 2018, and which claims foreign prioritybased on Australian (AU) Patent Application Serial No. 2017903658 filedon Sep. 8, 2017, the contents of all of which are incorporated herein byreference in their entireties.

TECHNICAL FIELD

The present invention relates to a method and system for verifying arecording. In particular, the present invention relates to a method andsystem for verifying the authenticity of a recording without disclosingthe contents of the recording.

BACKGROUND ART

In legal and legal-related proceedings, maintaining the integrity of therecord is a crucial job. For instance, the testimony of a witness or thestatements of an accused, if not properly preserved, can lead a judge orjury to make a wrong decision.

Typically, audio and/or video recordings are made during court hearings,and the electronic file of these recordings becomes the official recordof the proceedings. From time to time, a party in a proceeding before acourt may assert that the recording in the electronic file does notalign with their recollection of events, and has therefore been alteredor tampered with.

While the likelihood of a successful, undiscovered alteration of anelectronic file of this type is relatively low, the making of such anallegation may have serious ramifications both for the custodian of therecording and the proceedings of the court.

As a result, there would be an advantage if it were possible to providea reliable way in which to independently verify that the electronic filecontains an accurate and unaltered recording of the court proceedings.

It will be clearly understood that, if a prior art publication isreferred to herein, this reference does not constitute an admission thatthe publication forms part of the common general knowledge in the art inAustralia or in any other country.

SUMMARY OF INVENTION

The present invention is directed to method and system for verifying arecording which may at least partially overcome at least one of theabovementioned disadvantages or provide the consumer with a useful orcommercial choice.

With the foregoing in view, the present invention in one form, residesbroadly in a method for verifying a recording comprising the steps of:

-   -   a) Creating the recording using a first electronic device;    -   b) Generating, using the first electronic device, an electronic        recording file, the electronic recording file comprising        information based on the recording and one or more further        pieces of data associated with the recording;    -   c) Sending, using the first electronic device, the electronic        recording file to a certification server;    -   d) Generating, using the certification server, one or more        certification requests based on at least a portion of the        information in the electronic recording file, and sending the        one or more certification requests to a blockchain;    -   e) Receiving, with the certification server, confirmation of the        approval of the one or more certification requests by the        blockchain; and    -   f) Generating and/or displaying a verification confirmation on        the first electronic device.

The first electronic device may be of any suitable form. For instance,the first electronic device may be a computer, mobile telephone, tabletor the like. The recording may be made using any suitable technique.However, in a preferred embodiment of the invention, the recording maybe made using a software program provided on the first electronicdevice, an electronic application downloaded to the first electronicdevice and so on.

Any suitable form of recording may be made. For instance, the recordingmay be an audio recording, a video recording or both an audio and videorecording.

The recording may be a recording of anything capable of being recorded.However, it is envisaged that the method may be more usually used torecord an activity where it would be advantageous or desirable to ensurethat the recording is an accurate recording of the activity. Forinstance, the recording may be of a speech or lecture, a politicalactivity (such as a council or parliamentary session or the like), ascientific experiment and so on. More preferably, however, the recordingmay be a recording of a legal or legal-related proceeding, such as apolice interview, court hearing (or a hearing before a similar judicialbody), a deposition, a hearing before a disciplinary tribunal oradministrative body and the like, or any suitable combination thereof.

It is envisaged that the recording may comprise a recording of theentire proceeding (speech, lecture, political activity, interview, courthearing, deposition and so on), or the recording may comprise a portionof the overall proceeding (for instance, a session or a day of a courtcase and the like).

In other embodiments of the invention, the recording may comprise arelatively short part of the overall proceeding. In this embodiment, itis envisaged that a recording containing a relatively short part of theoverall proceeding may be verified while the proceeding is ongoing. Thismay be particularly advantageous for long proceedings (such as courthearings, police interviews and the like) where, instead of waitinguntil the completion of the proceeding to verify the recording, portionsof the proceeding may be periodically verified while the proceedingcontinues. This may be beneficial in that it may reduce the period oftime between the recording being created and its verification, reducingthe likelihood of the recording being tampered with.

The recording may comprise any suitable portion of the proceeding. Forinstance, the recording may comprise a portion of the proceeding inwhich a particular speaker was speaking, or in which a particular topicwas being discussed. In other embodiments, the proceeding may be dividedinto multiple recordings based on time intervals, such that eachproceeding comprises a plurality of recordings. In other words, arecording may comprise a period of time shorter than the total length ofthe proceeding.

The recording may be of any suitable length, and it is envisaged thatrecordings of the same proceeding may be of different lengths, or mayall be of the same length. The length of the recording is not critical,although it is preferable that the recording is relatively short so thatthe likelihood of the recording being tampered with between beingrecorded and verified is reduced or minimised. Thus, it is envisagedthat the length of the recording may be no more than one hour. Morepreferably, the length of the recording may be no more than 30 minutes.Yet more preferably, the length of the recording may be no more than 15minutes. Even more preferably, the length of the recording may be nomore than 10 minutes. Most preferably, the length of the recording maybe no more than 5 minutes.

It is envisaged that the length of the recording may be predetermined,such that recordings are created at predetermined time intervals. Thus,in this embodiment, the first electronic device may be adapted to createa recording at every predetermined time interval, even though theproceeding may be continuing. Preferably the verification of therecording occurs immediately upon, or soon after, the creation of therecording, so that the time between the creation of the recording andits verification is minimised.

In embodiments of the invention in which the recording is of a legal orlegal-related proceeding, it is envisaged that the first electronicdevice may comprise a computer located in the location where theproceeding is being held (such as a courtroom or the like). Preferably,the computer is provided with recording software in order to create therecording. Any suitable recording software may be provided, although ina preferred embodiment of the invention, the software may create adigital recording.

In a preferred embodiment of the invention, the recording may be storedin the memory of the first electronic device. The recording may bestored in any suitable electronic format. Alternatively, the recordingmay not be stored in the memory of the first electronic device, and mayinstead be sent to another electronic device (such as the certificationserver) for storage. In this embodiment of the invention, the recordingmay be sent continuously during the creation of the recording, or may besent at the conclusion of the recording. In another embodiment of theinvention, the recording may be stored on a storage medium, such as adisc, external hard drive, flash drive or the like, or a combinationthereof.

The recording may be stored or saved in any suitable format. Morespecifically, the recording may be stored or saved in any suitable fileformat. For instance, the recording may be stored or saved as one ormore of the following file types: AVI, ASF, MOV, QT, AVCHD, FLV, SWF,MPG, MP3, MP4, WMV, H.264, DivX, WAV, OGG, GSM, DCT, FLAC, AU, AIFF,VOX, RAW, WMA, AAC, ATRAC, RA, DSS, MSV or DVF. In a specific embodimentof the invention, the recording may be saved or stored as a TRM file.

As previously stated, an electronic recording file is generated by thefirst electronic device, the electronic recording file being based onthe recording and one or more further pieces of data associated with therecording.

It is envisaged that, in some embodiments of the invention, theelectronic recording file may include the recording. More preferably,however, the electronic recording file may be based on the recording,but may not comprise the recording itself. In this embodiment of theinvention, the electronic recording file may be based on any suitableinformation based on the recording. For instance, the electronicrecording file may comprise a hash function based on the recording. Morepreferably, the electronic recording file may comprise a cryptographichash function based on the recording.

In a specific embodiment of the invention, the electronic recording filemay comprise a cryptographic hash function from the SHA-2 set ofcryptographic hash functions. In particular, the electronic recordingfile may comprise an SHA-256 hash of the recording.

The one or more further pieces of data associated with the recording maybe of any suitable form. Preferably, however, the one or more furtherpieces of data may comprise metadata associated with the recording, thefirst electronic device and so on. It is envisaged that the one or morefurther pieces of data may include one or more of the file name of therecording, the first electronic device serial number, the serial numberof the motherboard of the first electronic device, information regardingthe network card of the first electronic device (such as the MACaddress, the IP address and so on), the details of any users of thefirst electronic device (such as the names of the users, the times anddates that users logged in and/or out of the first electronic deviceand/or the recording software), the date and time at which the recordingwas made, the geographic location at which the recording was made, thematter or proceeding to which the recording relates and so on.

The electronic recording file may be sent to the certification serverusing any suitable technique. For instance, the electronic recordingfile may be sent in the form of an email, SMS message, MMS message orthe like. More preferably, however, the electronic recording file may besent to the certification server as a machine-readable electronicmessage. In another embodiment of the invention, the electronicrecording file may be sent to the certification server via one or moreapplication programming interfaces (APIs). The electronic recording fileis preferably sent electronically, for instance using a Wi-Ficonnection, Bluetooth connection or the like, or a combination thereof.

It is envisaged that the electronic recording file may be sent to an APIrunning on the certification server, or may be running on a secondelectronic device (such as a computer, mobile telephone, tablet computeor the like) in electronic communication with the certification server.

In embodiments of the invention in which the electronic recording fileis in machine-readable format, it is envisaged that the certificationserver and/or the API associated with the certification server mayautomatically generate the one or more certification requests inresponse to receiving the electronic recording file. In some embodimentsof the invention, the certification server may also save or store theelectronic recording file. The electronic recording file may be saved orstored in electronic memory associated with the certification server(such as a hard drive or the like), remote memory (such as Cloudmemory), or on a storage medium, such as a disc, external hard drive,flash drive or the like, or a combination thereof.

As previously stated, the one or more certification requests are basedon at least a portion of the information in the electronic recordingfile. For instance, a certification request may be based on therecording, a hash function based on the recording, a cryptographic hashfunction based on the recording, at least one or the one or more furtherpieces of data associated with the recording, or any suitablecombination thereof.

In a preferred embodiment of the invention, a plurality of certificationrequests may be generated by the certification server (or, in someembodiments, an API associated with the certification server). In thisembodiment of the invention, it is envisaged that, while each of thecertification requests may contain some information that is common toother certification requests, no certification request is identical toanother certification request. For instance, in a specific embodiment ofthe invention, a pair of certification requests may be generated. Afirst certification request may be based on a cryptographic hashfunction based on the recording, while a second certification requestmay be based on a cryptographic hash function based on the recording incombination with the one or more further pieces of informationassociated with the recording.

The one or more certification requests may be sent to the blockchain inany suitable form. Preferably, however, the one or more certificationrequests are sent to the blockchain in machine-readable form. The one ormore certification requests are preferably sent electronically, forinstance using a Wi-Fi connection, Bluetooth connection or the like, ora combination thereof. Preferably, the action of sending the one or morecertification requests to the blockchain involves initiating thecreation of one or more new records on the blockchain. Preferably, ahash function (or a cryptographic hash function) of the contents of eachof the one or more certification requests is written to the blockchain.Preferably, a timestamp provided by the blockchain is also recorded. Theone or more certification requests may form a portion of a blockchain(such as one or more blocks within a blockchain, or a portion of a blockwithin a blockchain).

Any suitable blockchain may be used. However, in a preferred embodimentof the invention, the blockchain may be a public blockchain, or an opensource blockchain. In a specific embodiment of the invention, theblockchain may be the Hyperledger blockchain hosted by the LinuxFoundation.

If the one or more certification requests are successfully written tothe blockchain, the blockchain may send a confirmation notificationconfirming this to the confirmation server (or the API associated withthe confirmation server). Alternatively, the confirmation server (or theAPI associated with the confirmation server) may continuously orperiodically query the blockchain to determine whether the one or morecertification requests have been successfully written to the blockchain.Confirmation of the writing of the certification requests to theblockchain may be received in any suitable form. However, in a preferredembodiment of the invention, the confirmation of the writing of thecertification requests to the blockchain may be in the form ofblockchain record information.

In either event, once the confirmation server (or the API associatedwith the confirmation server) receives confirmation of the approval ofthe one or more certification requests (i.e. that the one or morecertification requests have been written to the blockchain), theconfirmation (for instance, in the form of the blockchain recordinformation) may be saved or stored in electronic memory associated withthe certification server (such as a hard drive or the like), remotememory (such as Cloud memory), or on a storage medium, such as a disc,external hard drive, flash drive or the like, or a combination thereof.

As previously stated, once confirmation of the approval of the one ormore certification requests is received, a verification confirmation isgenerated and/or displayed on the first electronic device. In someembodiments of the invention, the confirmation server (or the APIassociated with the confirmation server) may generate the verificationconfirmation and send it to the first electronic device. In theseembodiments of the invention, the verification confirmation may be sentin any suitable form, such as an email, SMS message, MMS message or thelike. More preferably, however, the verification confirmation may besent to the certification server as a machine-readable electronicmessage. The verification confirmation is preferably sentelectronically, for instance using a Wi-Fi connection, Bluetoothconnection or the like, or a combination thereof.

It is envisaged that, upon receipt of the verification confirmation, thefirst electronic device (or the recording software associated with thefirst electronic device) may record the verification confirmationagainst the recording and/or the electronic recording file. Theverification confirmation may be recorded electronically against therecording and/or the electronic recording file. Alternatively, theverification confirmation may be recorded electronically against therecording and/or the electronic recording file and the verificationconfirmation (or a notification confirming receipt of the verificationconfirmation) may be displayed on the first electronic device (or in therecording software associated with the first electronic device). Thenotification may be of any suitable form, such as a pop-up notificationfor a user, an audible or visual signal, a certificate or noticedisplayed on the first electronic device or the like. Alternatively, thenotification may be displayed within the recording software, forinstance in the form of text, symbols, or through a visual cue such as achange in the colour, size etc. of text within the recording software.

In an alternative embodiment of the invention, the confirmation servermay send the confirmation of the approval of the one or morecertification requests (for instance, in the form of the blockchainrecord information) to the first electronic device. In this embodimentof the invention, it is envisaged that, upon receipt of the confirmationof the approval of the one or more certification requests, the firstelectronic device (or the recording software associated with the firstelectronic device) may generate and/or display the verificationconfirmation.

Once generated, the verification confirmation may be recorded and/ordisplayed in the same manner as described previously.

In some embodiments of the invention, the first electronic device may beadapted to generate both the electronic recording file and the one ormore certification requests based on at least a portion of theinformation in the electronic recording file. In these embodiments ofthe invention, the first electronic device may be adapted to send theone or more certification requests to a blockchain. Thus, in a furtheraspect, the invention resides broadly in a method for verifying arecording comprising the steps of:

-   -   a) Creating the recording using a first electronic device;    -   b) Generating, using the first electronic device, an electronic        recording file, the electronic recording file comprising        information based on the recording and one or more further        pieces of data associated with the recording;    -   c) Generating, using the first electronic device, one or more        certification requests based on at least a portion of the        information in the electronic recording file, and sending the        one or more certification requests to a blockchain;    -   d) Receiving, with the first electronic device, confirmation of        the approval of the one or more certification requests by the        blockchain; and    -   e) Generating and/or displaying a verification confirmation on        the first electronic device.

In another aspect, the invention resides broadly in a method ofconfirming a verification of a recording by a blockchain, the methodcomprising the steps of:

-   -   a) Retrieving a recording from electronic memory associated with        a first electronic device;    -   b) Generating, using the first electronic device, an electronic        recording file, the electronic recording file comprising        information based on the recording and, optionally, one or more        further pieces of data associated with the recording;    -   c) Sending, using the first electronic device, the electronic        recording file to a certification server;    -   d) Retrieving, from electronic memory associated with the        certification server, blockchain record details associated with        the electronic recording file;    -   e) Sending, using the certification server, the blockchain        record details to the first electronic device;    -   f) Generating and/or displaying a verification confirmation        associated with the blockchain record details on the first        electronic device; and    -   g) Optionally verifying the electronic recording file with a        blockchain that generated the blockchain record details.

In some embodiments of the invention, the electronic recording filecomprises information based on the recording and one or more furtherpieces of data associated with the recording.

In some embodiments of the invention, the first electronic device may beadapted to generate the electronic recording file and the one or morecertification requests based on at least a portion of the information inthe electronic recording file. The first electronic device may also beadapted to retrieive, from electronic memory associated with the firstelectronic device, blockchain record details associated with theelectronic recording file. In these embodiments of the invention, thefirst electronic device may be adapted to send the one or morecertification requests to a blockchain. Thus, in yet another aspect, theinvention resides broadly in a method of confirming a verification of arecording by a blockchain, the method comprising the steps of:

-   -   a) Retrieving a recording from electronic memory associated with        a first electronic device;    -   b) Generating, using the first electronic device, an electronic        recording file, the electronic recording file comprising        information based on the recording and, optionally, one or more        further pieces of data associated with the recording;    -   c) Retrieving, from electronic memory associated with the first        electronic device, blockchain record details associated with the        electronic recording file;    -   d) Generating and/or displaying a verification confirmation        associated with the blockchain record details on the first        electronic device; and    -   e) Optionally verifying the electronic recording file with a        blockchain that generated the blockchain record details.

In a further aspect, the invention resides broadly in a system forverifying a recording, the system comprising:

-   -   at least one processor, at least one non-transitory computer        readable storage medium storing instructions thereon that, when        executed by the at least one processor, cause the system to:    -   verify an electronic recording file associated with the        recording and generated by a first electronic device, wherein        verifying the electronic recording file comprises generating one        or more certification requests, sending the one or more        certification requests to a blockchain, and receiving        confirmation of the approval of the one or more certification        requests by the blockchain.

Any of the features described herein can be combined in any combinationwith any one or more of the other features described herein within thescope of the invention.

The reference to any prior art in this specification is not, and shouldnot be taken as an acknowledgement or any form of suggestion that theprior art forms part of the common general knowledge.

BRIEF DESCRIPTION OF DRAWINGS

Preferred features, embodiments and variations of the invention may bediscerned from the following Detailed Description which providessufficient information for those skilled in the art to perform theinvention. The Detailed Description is not to be regarded as limitingthe scope of the preceding Summary of the Invention in any way. TheDetailed Description will make reference to a number of drawings asfollows:

FIG. 1 illustrates a flowchart of a method and system for verifying arecording according to an embodiment of the present invention.

FIG. 2 illustrates a flowchart of a method and system for verifying arecording according to an embodiment of the present invention.

FIG. 3 illustrates a screenshot of a step in a method for verifying arecording according to an embodiment of the present invention.

FIG. 4 illustrates a flowchart of a method and system for verifying arecording according to an embodiment of the present invention.

FIG. 5 illustrates a flowchart of a method and system for verifying arecording according to an embodiment of the present invention.

DESCRIPTION OF EMBODIMENTS

FIG. 1 illustrates a flowchart of a method and system for verifying arecording according to an embodiment of the present invention. In thisFigure, a recording 10 is made on recording software 11 running on afirst electronic device 12. In this embodiment, the first electronicdevice 12 is located in a courtroom, and the recording 10 is a video andaudio recording of a legal proceeding. The first electronic device 12 inthis embodiment is a computer.

The first electronic device 12 stores the recording 10 in the memory ofthe first electronic device 12 as an electronic file 101. In theembodiment of the invention shown in FIG. 1, the electronic file 101 isa TRM file.

The first electronic device 12 generates, from the electronic file 101,an electronic recording file 102. The electronic recording file 102 is acryptographic hash of the contents of the electronic file 101, and inparticular an SHA-256 hash of the contents of the electronic file 101.In addition, the electronic recording file 102 includes further piecesof data associated with the recording 10. In this embodiment, thefurther pieces of data include the name of the electronic file 101, themotherboard serial number of the first electronic device, the networkcard MAC address of the first electronic device 12 and the details ofthe user logged into the recording software 11 when the recording 10 wasmade.

The electronic recording file 102 is transmitted electronically to acloud-based certification server 13. The electronic recording file 102is received by an API 103 associated with the certification server 13.The API 103 both stores or saves the electronic recording file 102 tomemory 104 associated with the certification server 13 and alsogenerates a first certification request 15 and a second certificationrequest 16.

In the embodiment of the invention shown in FIG. 1, the firstcertification request 15 contains the SHA-256 hash of the contents ofthe electronic file 101. The second certification request 16 alsocontains the SHA-256 hash of the contents of the electronic file 101,along with the further pieces of data. Thus, the contents of the secondcertification request 16 are, in effect, the same as the contents of theelectronic recording file 102. Thus, while some of the information inthe first certification request 15 and the second certification request16 is the same, the first certification request 15 and the secondcertification request 16 are not identical to one another.

The first certification request 15 and the second certification request16 are transmitted electronically to a blockchain 17. The firstcertification request 15 is written to the blockchain 17 as a new record105, while the second certification request 16 is written to theblockchain as a new record 106. Along with the contents of the firstcertification request and the second certification request 16,respectively, the records 105, 106 also include a timestamp (i.e. a dateand time at which the records 105, 106 are written to the blockchain107) provided by the blockchain 107.

Once the certification requests 15, 16 are written to the blockchain 17,a confirmation service 107 periodically (or continuously, if preferred)queries the blockchain 17 to seek confirmation 109 of whether therecords 105, 106 have been successfully written to the blockchain 17. Itwill be understood that if the records 105, 106 are successfully writtento the blockchain 17, then the contents of the records 105, 106 (andtherefore the recording 10) are accepted as being correct and unaltered.

If the confirmation service 107 does not receive confirmation of therecords 105, 106 being written to the blockchain 17, a further query issent to the blockchain 17. On the other hand, if confirmation of thesuccessful writing of records 105, 106 to the blockchain 17 is receivedby the confirmation service 107, the blockchain record details 110 areelectronically transmitted to the certification server 13. Theblockchain record details 110 are saved or stored in memory 104associated with the certification server 13 and are also electronicallytransmitted to the first electronic device 12.

Upon receipt of the blockchain record details 110, the first electronicdevice 12 (or the recording software 11 associated with the firstelectronic device 12) generates a verification confirmation 112. Theverification confirmation 112 is associated with the recording 10 by therecording software 11. In the embodiment of the invention shown in FIG.1, the first electronic device 12 also displays the verificationconfirmation 112 on a display 14 of the first electronic device 12.While it is envisaged that the verification confirmation 112 may begenerated automatically by the first electronic device 12 on receipt ofthe blockchain record details 110, the display of the verificationconfirmation 112 may be in response to a user query, or may occurautomatically once the verification confirmation 112 is received.

FIG. 2 illustrates a flowchart of a method and system for verifying arecording according to an embodiment of the present invention. Morespecifically, FIG. 2 illustrates a method for confirming theverification of a recording.

In FIG. 2, a recording file 201 that is saved in the memory of a firstelectronic device 12 is loaded into playback software 202 running on thefirst electronic device 12. The first electronic device 12 (and theplayback software 202) generates an electronic recording file 203 thatis a cryptographic hash of the contents of the recording file 201, andin particular an SHA-256 hash of the contents of the recording file 201.In addition, the electronic recording file 203 includes further piecesof data associated with the recording file 201. In this embodiment, thefurther pieces of data include the name of the recording file 201.

The electronic recording file 203 is electronically transmitted to acloud-based certification server 13 and, in particular, a certificationAPI 204 associated with the certification server 13. The certificationAPI 204 retrieves data from memory associated with the certificationserver 13. In particular, the certification API 204 retrieves theblockchain record details 205 associated with the recording file 201.

The blockchain record details 205 are then electronically transmitted tothe first electronic device 12, and a verification confirmation 206 isdisplayed to a user. If desired, the electronic recording file 203 maybe independently verified on the blockchain 207.

FIG. 3 illustrates a screenshot of a step in a method for verifying arecording according to an embodiment of the present invention. In thisFigure, a plurality of recordings 300 are displayed to a user on aninterface 301.

When a verified recording 302 appears in the list, a verificationconfirmation 303 is displayed on the interface indicating that therecording 302 has been verified by a blockchain. As previouslymentioned, this indicates to a user that the recording 302 is a correctand unaltered recording of the, for instance, legal proceeding recordedtherein.

FIG. 4 illustrates a flowchart of a method and system for verifying arecording according to an embodiment of the present invention. In thisFigure, a recording 10 is made on recording software 11 running on afirst electronic device 12. In this embodiment, the first electronicdevice 12 is located in a courtroom, and the recording 10 is a video andaudio recording of a legal proceeding. The first electronic device 12 inthis embodiment is a computer.

The first electronic device 12 stores the recording 10 in the memory ofthe first electronic device 12 as an electronic file 101. In theembodiment of the invention shown in FIG. 1, the electronic file 101 isa TRM file.

The first electronic device 12 generates, from the electronic file 101,an electronic recording file 102. The electronic recording file 102 is acryptographic hash of the contents of the electronic file 101, and inparticular an SHA-256 hash of the contents of the electronic file 101.In addition, the electronic recording file 102 includes further piecesof data associated with the recording 10. In this embodiment, thefurther pieces of data include the name of the electronic file 101, themotherboard serial number of the first electronic device, the networkcard MAC address of the first electronic device 12 and the details ofthe user logged into the recording software 11 when the recording 10 wasmade.

Unlike the embodiment of the invention illustrated in FIG. 1, theelectronic recording file 102 is not transmitted electronically to acloud-based certification server. Instead, the first electronic device12 generates a first certification request 15 and a second certificationrequest 16 and transmits these electronically to a blockchain 17.

In the embodiment of the invention shown in FIG. 4, the firstcertification request 15 contains the SHA-256 hash of the contents ofthe electronic file 101. The second certification request 16 alsocontains the SHA-256 hash of the contents of the electronic file 101,along with the further pieces of data. Thus, the contents of the secondcertification request 16 are, in effect, the same as the contents of theelectronic recording file 102. Thus, while some of the information inthe first certification request 15 and the second certification request16 is the same, the first certification request 15 and the secondcertification request 16 are not identical to one another.

The first certification request 15 is written to the blockchain 17 as anew record 105, while the second certification request 16 is written tothe blockchain as a new record 106. Along with the contents of the firstcertification request and the second certification request 16,respectively, the records 105, 106 also include a timestamp (i.e. a dateand time at which the records 105, 106 are written to the blockchain107) provided by the blockchain 107.

Once the certification requests 15, 16 are written to the blockchain 17,a confirmation service 107 periodically (or continuously, if preferred)queries the blockchain 17 to seek confirmation 109 of whether therecords 105, 106 have been successfully written to the blockchain 17. Itwill be understood that if the records 105, 106 are successfully writtento the blockchain 17, then the contents of the records 105, 106 (andtherefore the recording 10) are accepted as being correct and unaltered.

If the confirmation service 107 does not receive confirmation of therecords 105, 106 being written to the blockchain 17, a further query issent to the blockchain 17. On the other hand, if confirmation of thesuccessful writing of records 105, 106 to the blockchain 17 is receivedby the confirmation service 107, the blockchain record details 110 areelectronically transmitted to the first electronic device 12. Theblockchain record details 110 are saved or stored in memory 104associated with the first electronic device 12.

Upon receipt of the blockchain record details 110, the first electronicdevice 12 (or the recording software 11 associated with the firstelectronic device 12) generates a verification confirmation 112. Theverification confirmation 112 is associated with the recording 10 by therecording software 11. In the embodiment of the invention shown in FIG.1, the first electronic device 12 also displays the verificationconfirmation 112 on a display 14 of the first electronic device 12.While it is envisaged that the verification confirmation 112 may begenerated automatically by the first electronic device 12 on receipt ofthe blockchain record details 110, the display of the verificationconfirmation 112 may be in response to a user query, or may occurautomatically once the verification confirmation 112 is received.

FIG. 5 illustrates a flowchart of a method and system for verifying arecording according to an embodiment of the present invention. Morespecifically, FIG. 5 illustrates a method for confirming theverification of a recording.

In FIG. 5, a recording file 201 that is saved in the memory of a firstelectronic device 12 is loaded into playback software 202 running on thefirst electronic device 12. The first electronic device 12 (and theplayback software 202) generates an electronic recording file 203 thatis a cryptographic hash of the contents of the recording file 201, andin particular an SHA-256 hash of the contents of the recording file 201.In addition, the electronic recording file 203 includes further piecesof data associated with the recording file 201. In this embodiment, thefurther pieces of data include the name of the recording file 201.

The first electronic device 12 retrieves, from electronic storage 204associated with the first electronic device 12, the blockchain recorddetails 205 associated with the recording file 201. The blockchainrecord details 205 and/or the electronic recording file 203 may beelectronically transmitted from the first electronic device 12 to theblockchain 207 for verification. Upon verification by the blockchain207, a verification confirmation 206 is displayed to a user on a display14 of the first electronic device 12.

An embodiment of the present invention also comprises a system forverifying a recording, the system comprising:

-   -   at least one processor, at least one non-transitory computer        readable storage medium storing instructions thereon that, when        executed by the at least one processor, cause the system to:    -   verify an electronic recording file associated with the        recording and generated by a first electronic device, wherein        verifying the electronic recording file comprises generating one        or more certification requests, sending the one or more        certification requests to a blockchain, and receiving        confirmation of the approval of the one or more certification        requests by the blockchain.

In the present specification and claims (if any), the word ‘comprising’and its derivatives including ‘comprises’ and ‘comprise’ include each ofthe stated integers but does not exclude the inclusion of one or morefurther integers.

Reference throughout this specification to ‘one embodiment’ or ‘anembodiment’ means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the present invention. Thus, theappearance of the phrases ‘in one embodiment’ or ‘in an embodiment’ invarious places throughout this specification are not necessarily allreferring to the same embodiment. Furthermore, the particular features,structures, or characteristics may be combined in any suitable manner inone or more combinations.

In compliance with the statute, the invention has been described inlanguage more or less specific to structural or methodical features. Itis to be understood that the invention is not limited to specificfeatures shown or described since the means herein described comprisespreferred forms of putting the invention into effect. The invention is,therefore, claimed in any of its forms or modifications within theproper scope of the appended claims (if any) appropriately interpretedby those skilled in the art.

The invention claimed is:
 1. A system for verifying a recording, thesystem comprising: at least one processor, at least one non-transitorycomputer readable storage medium storing instructions thereon that, whenexecuted by the at least one processor, cause the system to: verify anelectronic recording file comprising a cryptographic hash function basedon the recording and generated by a first electronic device, whereinverifying the electronic recording file comprises generating a pair ofcertification requests, wherein a first of the pair of certificationrequests is based on the cryptographic hash function, and a second ofthe pair of certification requests is based on the cryptographic hashfunction in combination with one or more further pieces of dataassociated with the recording, wherein the one or more further pieces ofdata comprise metadata associated with the recording and/or the firstelectronic device, sending the pair of certification requests to ablockchain, and receiving confirmation of the approval of the pair ofcertification requests by the blockchain.
 2. A system according to claim1 wherein the one or more further pieces of data associated with therecording include one or more of the file name of the recording, thefirst electronic device serial number, the serial number of themotherboard of the first electronic device, information regarding anetwork card of the first electronic device, details of any users of thefirst electronic device, date and time at which the recording was made,geographic location at which the recording was made and/or a matter orproceeding to which the recording relates.
 3. A system according toclaim 1 wherein the pair of certification requests are generated by acertification server.
 4. A system according to claim 1 wherein the pairof certification requests are sent to the Blockchain in machine-readableform.
 5. A system according to claim 1 wherein the confirmation of theapproval of the pair of certification requests by the blockchain isreceived in the form of blockchain record information.
 6. A systemaccording to claim 1 wherein, upon receiving confirmation of theapproval of the pair of certification requests by the blockchain thesystem generates and/or displays a verification confirmation on thefirst electronic device.
 7. A system according to claim 6 wherein theverification confirmation is recorded electronically against therecording and/or the electronic recording file by the first electronicdevice.
 8. A system according to claim 1 wherein the cryptographic hashfunction comprises an SHA-256 hash of the recording.
 9. A systemaccording to claim 1 wherein the recording is stored in the memory ofthe first electronic device.
 10. A system according to claim 1 whereinthe first electronic device comprises a computer.
 11. A system accordingto claim 1 wherein the electronic recording file is sent as amachine-readable electronic message to an API running on a certificationserver or a second electronic device, the second electronic device beingin electronic communication with the certification server.
 12. A systemaccording to claim 11 wherein the second electronic device comprises acomputer, mobile telephone or tablet computer.
 13. A system according toclaim 11 wherein the electronic recording file is saved or stored inelectronic memory associated with the certification server, remotememory or on a storage medium.
 14. A system according to claim 1 whereinsending the pair of certification requests to the blockchain initiatesthe creation of one or more new records on the blockchain.
 15. A systemaccording to claim 1 wherein the pair of certification requests form aportion of the blockchain.
 16. A system according to claim 1 wherein theconfirmation of the approval of the pair of certification requests bythe blockchain is received by a confirmation server or an API associatedwith the confirmation server.
 17. A system according to claim 1 whereinthe confirmation of the approval of the pair of certification requestsby the blockchain is received in the form of blockchain recordinformation.
 18. A system according to claim 17 wherein the blockchainrecord information includes a timestamp provided by the blockchain. 19.A system according to claim 1 wherein, upon receipt of the confirmationof the approval of the pair of certification requests by the blockchain,a verification confirmation is generated and/or displayed on the firstelectronic device.
 20. A system according to claim 19 wherein, uponreceipt of the verification confirmation, the first electronic devicerecords the verification confirmation against the recording and/or theelectronic recording file.